Data processing method and nvme storage device

ABSTRACT

A data processing method and a storage apparatus are disclosed. The data processing method includes: receiving, by an NVMe storage device, an NVMe write command sent by a host, where the NVMe write command carries a key and a value pointer, the value pointer points to first storage space, and the first storage space is used to store a value; obtaining, by the NVMe storage device, the key from the NVMe write command and a value length, and allocating second storage space to the value according to the value length, where the second storage space is in the NVMe storage device; and obtaining, by the NVMe storage device, the value from the host, and storing the value in the second storage space.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.16/899,294, filed on Jun. 11, 2020, which is a continuation of U.S.patent application Ser. No. 15/971,990, filed on May 4, 2018, now U.S.Pat. No. 10,705,974, which is a continuation of InternationalApplication No. PCT/CN2016/103268, filed on Oct. 25, 2016, which claimspriority to Chinese Patent Application No. 201510998928.8, filed on Dec.28, 2015. All of the aforementioned patent applications are herebyincorporated by reference in their entireties.

TECHNICAL FIELD

Embodiments of the present disclosure relate to the storage field, andin particular, to the NVMe field.

BACKGROUND

The NVMe (non-volatile memory express) protocol is a high-speedinterface protocol used in a storage system. Compared with the SCSIprotocol, the NVMe protocol provides a higher read/write speed and alower delay, and therefore, attracts more attention of the industry andbecomes increasingly popular.

With development of information technologies, an object storagetechnology is frequently used. A common object storage technology is keyvalue (KV) storage. In the prior art, because an NVMe device supportsonly a block interface, if a host needs to store KV data in an NVMestorage device, steps are as follows: The host needs to convert a KVcommand (generally, including a key, a value, and metadata) into a datablock (for example, the host splits one KV command into at least twodata blocks, or combines KV commands into one data block). The hostallocates an LBA address to the data block. The host sends the datablock to the NVMe storage device. After receiving the data block, theNVMe storage device successively stores data blocks according to theallocated LBA address.

However, in the foregoing steps, converting the KV data into the datablock and allocating the LBA address to the data block consume a largequantity of computing resources of the host. Consequently, performanceof the storage system deteriorates, and running efficiency of the hostand a storage controller is affected.

SUMMARY

The present disclosure provides solutions to a data processing method,an NVMe storage device, and a storage system, so that efficiency ofwriting KV data into an NVMe storage device can be improved. In somesolutions, correspondingly, efficiency of reading the KV data from theNVMe storage device is also improved.

A first aspect of embodiments of the present disclosure provides a dataprocessing method. The method includes: receiving, by a non-volatilememory express NVMe storage device, an NVMe write command sent by ahost, where the NVMe write command carries a key, the NVMe write commandcarries a value pointer, the value pointer points to first storage spacein the host, the first storage space is used to store a value, and thekey and the value belong to a same KV pair; obtaining, by the NVMestorage device, the key from the NVMe write command, obtaining a valuelength according to the value pointer, and allocating second storagespace to the value according to the value length, where the secondstorage space is in the NVMe storage device; and sending, by the NVMestorage device, a first transmission request to the host, obtaining thevalue from the host, and storing the value in the second storage space.Based on this solution, in a process of transmitting KV data from thehost to the NVMe storage device, the KV data does not need to beconverted into a block form, so that KV data storage efficiency isimproved.

In a first possible implementation of the first aspect, the sending, bythe NVMe storage device, a first transmission request to the host andobtaining the value from the host specifically includes: sending, by theNVMe storage device, a DMA transmission request to the host, andobtaining the value from the host, where the DMA instruction carries thefirst storage space as an access address, and carries the second storagespace as a write address, where the NVMe storage device and the host areconnected by using a PCIe bus. This solution provides a valuetransmission manner implemented in a DMA manner.

In a second possible implementation of the first aspect, the sending, bythe NVMe storage device, a first transmission request to the host andobtaining the value from the host specifically includes: sending, by thestorage device, an RDMA transmission request to the host, and obtainingthe value from the host, where the RDMA instruction carries the firststorage space as an access address, and carries the second storage spaceas a write address, where the NVMe storage device and the host areconnected by using a Fabric bus. This solution provides a valuetransmission manner implemented in an RDMA manner.

In a third possible implementation of the first aspect, the NVMe writecommand further carries a KV quantity field, where the KV quantity fieldis used to describe a quantity of KVs in the NVMe write command, so thatthe NVMe storage device obtains, from the NVMe write command, keys whosequantity is the same as the quantity of KVs, and obtains values whosequantity is the same as the quantity of KVs. In this solution, aplurality of KVs may be carried in a same NVMe write command.

In a fourth possible implementation of the first aspect, the NVMe writecommand further carries a KV format field, where the KV format fielddescribes a field structure in the NVMe write command, so that the NVMestorage device obtains each field from the NVMe write command accordingto field content defined by the KV format field. In this solution, asame NVMe device may be enabled to support multiple formats of NVMewrite command packets for transmitting the KV. In a specific writeoperation process, a write command in one of the multiple formats isused. Similarly, in a process of a read command, a same NVMe device mayalso be enabled to support multiple formats of NVMe read command packetsfor transmitting the KV.

In a fifth possible implementation of the first aspect, the NVMe writecommand further carries the value metadata pointer, and the methodfurther includes: obtaining, by the NVMe storage device, a metadatalength according to the metadata pointer, and allocating fourth storagespace to the metadata according to the metadata length, where the fourthstorage space is in the NVMe storage device; and obtaining, by the NVMestorage device, the metadata from the host by using the firsttransmission request, and storing the metadata in the fourth storagespace. A specific solution of storing the metadata in the KV isdescribed in this solution.

With reference to the fifth possible implementation of the first aspect,in a sixth possible implementation, the method includes: after themetadata fails to be transmitted, releasing, by the NVMe storage device,the storage space allocated to the value, and releasing the fourthstorage space allocated to the metadata. In this solution, a resourceoccupied by the value may be released in a timely manner after themetadata fails to be transmitted.

In a seventh possible implementation of the first aspect, the sending,by the NVMe storage device, a first transmission request to the host andobtaining the value from the host specifically includes one of thefollowing: sending, by the storage device, at least two DMA transmissionrequests to the host, so as to obtain the value, where each DMAtransmission request is used to request to obtain a part of the value,and when any DMA transmission request fails to be executed, releasing,by the NVMe storage device, the storage space allocated to the value,where the NVMe storage device and the host are connected by using a PCIebus; or sending, by the storage device, at least two RDMA transmissionrequests to the host, so as to obtain the value, where each RDMAtransmission request is used to request to obtain a part of the value,and when any RDMA transmission request fails to be executed, releasing,by the NVMe storage device, the storage space allocated to the value,where the NVMe storage device and the host are connected by using theFabric. In this solution, a same value may be separately transmitted byusing multiple RDMA transmission requests, so as to reduce an amount ofdata in each RDMA transmission.

In an eighth possible implementation of the first aspect, the methodfurther includes: generating a mapping relationship between the key andthe second storage space. The mapping relationship may provide a basisfor a subsequent solution of reading the KV (especially the value).

In a ninth possible implementation of the first aspect, after theforegoing method, the method further includes: receiving, by the NVMestorage device, an NVMe read command from the host, where the NVMe readcommand carries the key. In addition, the method may further include:searching, by the NVMe storage device, the mapping relationshipaccording to the key, obtaining location information of the secondstorage space in which the value is stored, and sending the locationinformation of the second storage space to the host; and receiving, bythe NVMe storage device, a second transmission request sent by the host,where the second transmission request is used to request to obtain datastored in the second storage space. According to the nine possibleimplementation of the first aspect, reading of the KV (or the value) maybe implemented.

In a tenth possible implementation of the first aspect, before thereceiving, by the NVMe storage device, a second transmission requestsent by the host, the method further includes: reserving, by the host,third storage space in the host according to a size of the secondstorage space; and after the sending, by the NVMe storage device, thevalue to the host, the method further includes: writing, by the host,data received from the second storage space into the fourth storagespace. Operations performed by the host in a process of reading the KV(or the value) are described in this solution.

In an eleventh possible implementation of the first aspect, the NVMeread command that is sent by the host and that is received by the NVMestorage device further carries free space information of the host, andafter the receiving, by the NVMe storage device, an NVMe read commandfrom the host, the method further includes: determining, by the NVMestorage device, whether free storage space in the host is greater thanor equal to the second storage space; and if the free storage space inthe host is greater than or equal to the second storage space,performing the step of sending the location information of the secondstorage space to the host, or if the free storage space in the host isnot greater than or equal to the second storage space, ending the step.In this solution, the free space information of the host is carried inthe NVMe read command, so that after receiving the response of the NVMestorage device, the NVMe storage device has informed of spaceinformation of the host, thus, the host does not need to determinewhether the free space is enough or reserve storage space. This mayreduce interaction times between the NVMe storage device and the host,thereby improving efficiency of reading the value by the host. It shouldbe noted that free space herein means a space with contiguous address.

In a twelfth possible implementation of the first aspect, the firststorage space is described by using a start address of the first storagespace and the value length; and the second storage space is described byusing a start address of the second storage space. A description mannerof the storage space is described in this solution. According to contentdescribed in this description manner, a storage location from which thevalue is read and a storage location into which the value is written maybe located.

According to a second aspect, the present disclosure provides animplementation of an NVMe storage device. The NVMe storage deviceincludes a controller and a storage medium, where the controller isconnected to the storage medium, and the storage medium is configured toprovide storage space, where the processor is configured to: receive, anon-volatile memory express NVMe write command sent by a host, where theNVMe write command carries a key, the NVMe write command carries a valuepointer, the value pointer points to first storage space in the host,the first storage space is used to store a value, and the key and thevalue belong to a same KV pair; obtain the key from the NVMe writecommand, obtain a value length according to the value pointer, andallocate second storage space to the value according to the valuelength, where the second storage space is in the storage medium; andsend a first transmission request to the host, obtain the value from thehost, and store the value in the second storage space. The NVMe storagedevice is configured to perform methods in the first aspect and invarious implementations of the first aspect.

A third aspect of the present disclosure provides an implementationmethod for a data processing method. The method includes: receiving, bya non-volatile memory express NVMe storage device, an NVMe writecommand, where a header of the NVMe write command carries a key key, theNVMe command further carries a value value, the key is corresponding tothe value, and the key and the value belong to a same KV pair;obtaining, by the NVMe storage device, the key and the value from theNVMe write command; and storing, by the NVMe storage device, the valuein a storage medium in the NVMe storage device.

In a first possible implementation of the third aspect, the NVMe writecommand further carries a KV quantity field, where the KV quantity fieldis used to describe a quantity of KVs in the NVMe write command, so thatthe NVMe storage device obtains, from the NVMe write command, keys whosequantity is the same as the quantity of KVs, and obtains values whosequantity is the same as the quantity of KVs.

In a second possible implementation of the third aspect, the NVMe writecommand further carries a KV format field, where the KV format fielddescribes a field structure in the NVMe write command, so that the NVMestorage device obtains each field from the NVMe write command accordingto field content defined by the KV format field.

In a third possible implementation of the third aspect, the NVMe writecommand further carries a key length, and the obtaining, by the NVMestorage device, the key from the write command specifically includes:obtaining the key from the write command from a preset start location ofthe key and according to the key length.

In a fourth possible implementation of the third aspect, the NVMe writecommand further carries a value offset and a value length, where theobtaining, by the NVMe storage device, the value from the NVMe writecommand specifically includes: obtaining, by the NVMe storage deviceaccording to the value length, the value from a location indicated bythe offset.

In a fifth possible implementation of the third aspect, the methodfurther includes: generating a mapping relationship between the key andthe value storage space.

A six possible implementation is based on the fifth possibleimplementation of the third aspect of this application. After theforegoing method, the method further includes: sending, by a host, anNVMe read command to the NVMe storage device, where the NVMe readcommand carries the key; receiving, by the NVMe storage device, the readcommand from the host, and obtaining the key from the NVMe read command;searching, by the NVMe storage device and by using the key, the mappingrelationship for the value storage space; obtaining, by the NVMe storagedevice, the value from the value storage space; and generating, by theNVMe storage device, a response message of the NVMe read command, andsending the response message to the host, where the response messagecarries the value.

According to a fourth aspect, the present disclosure provides animplementation of an NVMe storage device. The NVMe storage deviceincludes a controller and a storage medium. The controller is configuredto perform methods in the third aspect and in various implementations ofthe third aspect.

A fifth aspect of the embodiments of the present disclosure provides astorage apparatus. The storage apparatus may be a physical device, forexample, an NVMe storage device; or may be a logical device, forexample, a program running on a processor in an NVMe storage device, ora program in a storage server. The apparatus includes: an interfacemodule, configured to receive an NVMe write command sent by a host,where the NVMe write command carries a key, the NVMe write commandcarries a value pointer, the value pointer points to first storage spacein the host, the first storage space is used to store a value, and thekey and the value belong to a same KV pair; a processing module,configured to: obtain the key from the NVMe write command, obtain avalue length according to the value pointer, and allocate second storagespace to the value according to the value length; and a storage module,configured to: send a first transmission request to the host, obtain thevalue from the host, and store the value in the second storage space.The second storage space may be provided by a storage medium in the NVMestorage device. The storage medium is connected to a processor in theNVMe storage device. Based on this solution, in a process oftransmitting KV data from the host to the NVMe storage device, the KVdata does not need to be converted into a block form, so that KV datastorage efficiency is improved.

In a first possible implementation of the fifth aspect, that the storagemodule sends a first transmission request to the host and obtains thevalue from the host specifically includes: sending, by the storagemodule, a DMA transmission request to the host, and obtaining the valuefrom the host, where the DMA instruction carries the first storage spaceas an access address, and carries the second storage space as a writeaddress. The storage apparatus (the storage apparatus is hardware) andthe host are connected by using a PCIe bus, or the NVMe storage devicein which the storage apparatus (the storage apparatus is software) islocated and the host are connected by using a PCIe bus. This solutionprovides a value transmission manner implemented in a DMA manner.

In a second possible implementation of the fifth aspect, that thestorage module sends a first transmission request to the host andobtains the value from the host specifically includes: sending, by thestorage module, an RDMA transmission request to the host, and obtainingthe value from the host, where the RDMA instruction carries the firststorage space as an access address, and carries the second storage spaceas a write address. The storage apparatus (the apparatus is hardware)and the host are connected by using a Fabric bus, or the NVMe storagedevice in which the storage apparatus (the storage apparatus issoftware) is located and the host are connected by using a Fabric bus.This solution provides a value transmission manner implemented in anRDMA manner.

In a third possible implementation of the fifth aspect, the NVMe writecommand further carries a KV quantity field, where the KV quantity fieldis used to describe a quantity of KVs in the NVMe write command, so thatthe NVMe storage device obtains, from the NVMe write command, keys whosequantity is the same as the quantity of KVs, and obtains values whosequantity is the same as the quantity of KVs. In this solution, aplurality of KVs may be carried in a same NVMe write command.

In a fourth possible implementation of the fifth aspect, the NVMe writecommand further carries a KV format field, where the KV format fielddescribes a field structure in the NVMe write command, so that the NVMestorage device obtains each field from the NVMe write command accordingto field content defined by the KV format field. In this solution, asame NVMe device may be enabled to support multiple formats of NVMewrite command packets for transmitting the KV. In a specific writeoperation process, a write command in one of the multiple formats isused. Similarly, in a process of a read command, a same NVMe device mayalso be enabled to support multiple formats of NVMe read command packetsfor transmitting the KV.

In a fifth possible implementation of the fifth aspect, the NVMe writecommand further carries the value metadata pointer, and the methodfurther includes: obtaining, by the NVMe storage device, a metadatalength according to the metadata pointer, and allocating fourth storagespace to the metadata according to the metadata length, where the fourthstorage space is in the NVMe storage device; and obtaining, by the NVMestorage device, the metadata from the host by using the firsttransmission request, and storing the metadata in the fourth storagespace. A specific solution of storing the metadata in the KV isdescribed in this solution.

With reference to the fifth possible implementation of the fifth aspect,in a sixth possible implementation, after the metadata fails to betransmitted, the processing module is further configured to: release thestorage space allocated to the value, and release the fourth storagespace allocated to the metadata. In this solution, a resource occupiedby the value may be released in a timely manner after the metadata failsto be transmitted.

In a seventh possible implementation of the fifth aspect, that thestorage module sends a first transmission request to the host andobtains the value from the host specifically includes one of thefollowing: sending, by the processing module, at least two DMAtransmission requests to the host, so as to obtain the value, where eachDMA transmission request is used to request to obtain a part of thevalue, and when any DMA transmission request fails to be executed,releasing, by the storage module, the storage space allocated to thevalue, where the NVMe storage device and the host are connected by usinga PCIe bus; or sending, by the storage module, at least two RDMAtransmission requests to the host, so as to obtain the value, where eachRDMA transmission request is used to request to obtain a part of thevalue, and when any RDMA transmission request fails to be executed,releasing, by the storage module, the storage space allocated to thevalue, where the NVMe storage device and the host are connected by usingthe Fabric. In this solution, a same value may be separately transmittedby using multiple RDMA transmission requests, so as to reduce an amountof data in each RDMA transmission.

In an eighth possible implementation of the fifth aspect, the processingmodule is further configured to generate a mapping relationship betweenthe key and the second storage space. The mapping relationship mayprovide a basis for a subsequent solution of reading the KV (especiallythe value).

In a ninth possible implementation of the fifth aspect, the interfacemodule is further configured to receive an NVMe read command from thehost, where the NVMe read command carries the key. The processing moduleis further configured to search the mapping relationship according tothe key, obtain location information of the second storage space inwhich the value is stored, and the processing module is furtherconfigured to send the location information of the second storage spaceto the host by using the interface module. The interface module isfurther configured to receive a second transmission request sent by thehost, where the second transmission request is used to request to obtaindata stored in the second storage space. According to the eighthpossible implementation of the fifth aspect, reading of the KV (or thevalue) may be implemented.

In a tenth possible implementation of the fifth aspect, before theinterface module receives a second transmission request sent by thehost, the host is further configured to reserve third storage space inthe host according to a size of the second storage space. After thestorage apparatus sends the value to the host, the host is furtherconfigured to write data received from the second storage space into thefourth storage space. A function of reading the KV (or the value) by thehost is described in this solution.

In an eleventh possible implementation of the fifth aspect, the NVMeread command that is sent by the host and that is received by theinterface module further carries free space information of the host, andafter the receiving, by the NVMe storage device, an NVMe read commandfrom the host, the method further includes: determining, by the NVMestorage device, whether free storage space in the host is greater thanor equal to the second storage space; and if the free storage space inthe host is greater than or equal to the second storage space,performing the step of sending the location information of the secondstorage space to the host, or if the free storage space in the host isnot greater than or equal to the second storage space, ending the step.In this solution, the free space information of the host is carried inthe NVMe read command, so that after receiving the response of the NVMestorage device, the host does not need to determine whether the freespace is enough or reserve storage space. This may reduce interactiontimes between the NVMe storage device and the host, thereby improvingefficiency of reading the value by the host. It should be noted thatfree space herein means a contiguous address space.

In a twelfth possible implementation of the fifth aspect, the firststorage space is described by using a start address of the first storagespace and the value length; and the second storage space is described byusing a start address of the second storage space. A description mannerof the storage space is described in this solution. According to contentdescribed in this description manner, a storage location from which thevalue is read and a storage location into which the value is written maybe located.

According to a sixth aspect, with reference to the storage apparatusprovided in the fifth aspect and the possible implementations of thefifth aspect, the present disclosure further provides an implementationof a storage system. The storage system includes a host and a storageapparatus.

A seventh aspect of the present disclosure provides a storage apparatus.The storage apparatus may be a physical device, for example, an NVMestorage device; or may be a logical device, for example, a programrunning on a processor in an NVMe storage device, or a program in astorage server. The apparatus includes: an interface module, configuredto receive an NVMe write command, where a header of the NVMe writecommand carries a key key, the NVMe command further carries a valuevalue, the key is corresponding to the value, and the key and the valuebelong to a same KV pair; a processing module, configured to obtain thekey and the value from the NVMe write command; and a storage module,configured to store the value in the storage medium in the NVMe storagedevice.

In a first possible implementation of the seventh aspect, the NVMe writecommand further carries a KV quantity field, where the KV quantity fieldis used to describe a quantity of KVs in the NVMe write command, so thatthe processing module obtains, from the NVMe write command, keys whosequantity is the same as the quantity of KVs, and obtains values whosequantity is the same as the quantity of KVs.

In a second possible implementation of the seventh aspect, the NVMewrite command further carries a KV format field, where the KV formatfield describes a field structure in the NVMe write command, so that theprocessing module obtains each field from the NVMe write commandaccording to field content defined by the KV format field.

In a third possible implementation of the seventh aspect, the NVMe writecommand further carries a key length, and that the processing moduleobtains the key from the write command specifically includes: obtainingthe key from the write command from a preset start location of the keyand according to the key length.

In a fourth possible implementation of the seventh aspect, the NVMewrite command further carries a value offset and a value length, andthat the processing module obtains the value from the NVMe write commandspecifically includes: obtaining, by the processing module according tothe value length, the value from a location indicated by the offset.

In a fifth possible implementation of the seventh aspect, the storagemodule is further configured to generate a mapping relationship betweenthe key and the value storage space.

Based on the fifth possible implementation of the seventh aspect, aseventh possible implementation provides an implementation of the host.The host is configured to send an NVMe read command to the NVMe storagedevice, where the NVMe read command carries the key. The interfacemodule is further configured to: receive the read command from the host,and obtain the key from the NVMe read command. The processing module isfurther configured to search, by using the key, the mapping relationshipfor the value storage space; the processing module is further configuredto obtain the value from the value storage space; and the processingmodule is further configured to: generate a response message of the NVMeread command, and send the response message to the host by using theinterface module, where the response message carries the value.

According to an eighth aspect, with reference to the storage apparatusprovided in the seventh aspect and the possible implementations of theseventh aspect, the present disclosure further provides animplementation of a storage system. The storage system includes a hostand a storage apparatus.

According to a ninth aspect, with reference to the storage deviceprovided in the second aspect and the possible implementations of thesecond aspect, the present disclosure further provides an implementationof a storage system. The storage system includes a host and an NVMestorage device.

According to a tenth aspect, with reference to the storage deviceprovided in the fourth aspect and the possible implementations of thefourth aspect, the present disclosure further provides an implementationof a storage system. The storage system includes a host and a storageapparatus.

Based on the solutions to the data processing method, the NVMe storagedevice, and the storage system that are provided in the presentdisclosure, efficiency of writing KV data into an NVMe storage devicecan be improved.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a flowchart of an embodiment of a data processing method;

FIG. 2 is a schematic diagram of an NVMe command format;

FIG. 3 is a schematic diagram of an NVMe command format;

FIG. 4 is a schematic diagram of an NVMe command format;

FIG. 5 is a schematic diagram of an NVMe command format;

FIG. 6 is a schematic diagram of a mapping relationship among a key, avalue storage location, and a metadata storage location;

FIG. 7 is a topology view of an embodiment of a hardware topology of adata processing system;

FIG. 8 is a flowchart of an embodiment of a data processing method;

FIG. 9 is a schematic diagram of a command format;

FIG. 10 is a schematic diagram of a command format;

FIG. 11 is a schematic diagram of a command format;

FIG. 12 is a flowchart of an embodiment of a method for writing data;

FIG. 13 is a flowchart of an embodiment of a method for reading data;

FIG. 14A and FIG. 14B are a flowchart of an embodiment of a method forwriting data; and

FIG. 15 is a diagram of a logical function of an embodiment of a dataprocessing system.

DESCRIPTION OF EMBODIMENTS

Non-volatile memory express (NVMe) is a logical device interface, andmay support accessing a non-volatile storage medium by using a PCIe bus.The NVMe interface may be used on a storage device of a flash medium,for example, a solid state disk SSD. A device with an NVMe interface isreferred to as an NVMe device. An NVMe storage device is a type of NVMedevice, and refers to an NVMe device having a storage function. Thefollowing mainly uses the NVMe storage device (in embodiments of thepresent disclosure, the NVMe storage device is referred to as a storagedevice for short) as an example for description.

KV storage, also referred to as K/V storage, is a storage technology. Inthe KV storage, a key-value pair is a basic data model. The key-valuepair may include a key and a value. After being extended, the key-valuepair may further include metadata. A key uniquely identifies a value.

If a host sends KV data to the NVMe storage device in a block manner forstorage, operations that need to be performed by the host include: firstconverting the KV data into a block form; then allocating a logicalblock address (LBA) on the storage device to a block; and next,generating a write command, where the write command carries the blockand the LBA of the block; and after receiving the block, storing, by theNVMe storage device, the block according to a physical addresscorresponding to the LBA. If the KV data needs to be read, a data blockneeds to be read first, and then the data block needs to be convertedinto the KV data. In a process of writing the KV data, allocating theLBA address and converting the KV data into the data block need toconsume a lot of time and system resources that are of the host,increasing a system delay. In a process of reading the KV data, the hostneeds to send location information (for example, a start address and alength) of a to-be-read block to the NVMe storage device, obtain thedata block, and re-convert the data block into the KV data. This alsoconsumes a large quantity of computing resources of the host, increasinga system delay.

This application is applicable to an NVMe scenario and an NVMe overFabric (NOF) scenario. In the NVMe scenario, a host and a storage deviceare connected by using a bus (for example, a PCIe bus). In thisscenario, the storage device is used as a component of the host. Forexample, the host is a server, and the storage device is an NVMeinterface solid state disk (SSD) in the server. In the NOF scenario, ahost and a storage device are connected by using the Fabric (forexample, the Ethernet or the FC). The host includes a memory, aprocessor, and an interface. The host and the storage device may be twodevices independent of each other. In the embodiments of the presentdisclosure, the host is an initiator of a read request or a writerequest, and the storage device is a responder of the data request orthe write request and is also referred to as a target.

In the embodiments of the present disclosure, the existing NVMe protocolmay be extended, and a new NVMe command is proposed. The new NVMecommand is an extension and optimization of an existing NVMe command(for example, an NVMe command defined in the NVMe standard protocol1.2.1, or an NVMe command defined in the NVMe over Fabric standardprotocol 1.0), so that an NVMe device may directly support a KVinterface.

Because the NVMe device may directly support the KV interface, the KVdata may be directly transmitted between the storage device and the hostby using the NVMe protocol. The host may directly write the KV data intothe storage device by using the NVMe protocol, or directly read the KVfrom the storage device by using the NVMe protocol. Therefore, comparedwith the prior art, repeated conversion between a KV format and a blockformat is avoided between the storage device and the host, therebyreducing system complexity and improving system performance. Unlessotherwise specified, all NVMe commands in the embodiments of the presentdisclosure are extended NVMe commands.

In an optional implementation, a key is directly carried in a commandheader of the NVMe command. Therefore, the key may be obtained bydirectly reading the command header of the NVMe (with no need to parse apayload of the NVMe command).

A value may be carried in the NVMe command, and the value may beobtained by reading the NVMe command. In addition, alternatively, theNVMe command may not directly carry the value, but carries a valuepointer. The value pointer directly or indirectly points to valuestorage space. The value may be obtained from the value storage space byusing a DMA/an RDMA technology.

The following describes nouns that may appear in the embodiments of thepresent disclosure.

The following parameters are added to an existing NVMe write command; ora new NVMe KV write command is defined, and may include the followingparameters.

Number of KV: a quantity of KVs transmitted in an NVMe command. A KVincludes a key and a value corresponding to the key. Alternatively, a KVincludes a key and a value pointer. The value pointer points to valuestorage space, and a value is corresponding to the key.

Value: data that may be stored in a storage device or read from thestorage device, for example, a movie.

Key: uniquely identifies a value. The key may also be referred to as akey code. A combination of a key and a corresponding value may bereferred to as a KV or a KV pair (pair).

KV (key value): a combination of a key and a value, also referred to asa KV pair. Optionally, the KV further includes metadata.

Metadata: used to describe an attribute of a value. For example, if avalue is a movie, the metadata may include, but is not limited to,information such as a movie name, duration, or starring.

Common header: a part of a command header, referring to a part that isin the command header and that is the same as that in an existing NVMecommand header.

KV format ID: indicates a format of a current NVMe command, or definescontent of each field in the NVMe command. NVMe commands fortransmitting a KV may be in multiple command formats, and are identifiedby using a KV format ID. NVMe packets in different command formats mayhave different fields, or different field arrangement orders.

Key length: describes a length of a key.

Value length: describes a length of a value.

Metadata length: describes a length of metadata.

Key offset: describes an offset of a key in an NVMe command.

Value offset: describes an offset of a value in an NVMe command.

Metadata offset: describes an offset of metadata in an NVMe command.

DPTR (Data Pointer): a data pointer, pointing to to-be-transmitted data.

MPTR (Metadata Pointer): a metadata pointer, pointing toto-be-transmitted metadata.

PRP (Physical Region Page) entry: a physical region page instance (orreferred to as a physical region page format entry), which may be usedto record a pointer. The PRP is one of two data transmission protocolsfrequently used in the NVMe protocol, and may be used for an NVMe overPCIe architecture. The PRP entry may point to a pointer of a physicalmemory page.

SGL (Scatter Gather List) Entry: a scatter gather list instance (orreferred to as a scatter gather list format entry), which may be used torecord a pointer. The SGL is one of the two data transmission protocolsfrequently used in the NVMe protocol, and may be used for an NVMe overPCIe/Fabric architecture.

Referring to FIG. 1 , the present disclosure provides an embodiment of adata processing method. The method may be used between an NVMe storagedevice and a host.

11. A host generates an NVMe write command (hereinafter referred to as awrite command for short), and sends the write command to a storagedevice, where the write command carries a value and a key correspondingto the value. The write command is sent to an NVMe storage device byusing an NVMe interface on the host. The key and the value may becarried in a payload, or may be carried in a command header.

In this step, the key may be carried in the command header, or may becarried in the payload. In the embodiments of the present disclosure,unless otherwise stated, a field carried in a write command/a readcommand may be in a command header, or may be in a payload. For example,the value may be carried in the command header, or may be carried in thepayload.

Optionally, if the write command carries more than one KV, the writecommand may further carry a “number of KV”, so as to describe a quantityof KVs. After receiving the write command, the storage device may readthe KV according to the quantity of KVs that is indicated by the numberof KV, and stop reading after all KVs are read. Alternatively, aterminator may be used to indicate end of the KVs, and the storagedevice stops reading after reading the terminator.

Optionally, the write command further carries a KV format ID. NVMecommands for transmitting a KV may be in multiple command formats. Fordifferent command formats, fields may be different, and locations of thefields may also be different. The KV format ID is used to indicate acommand format used by this command.

A location of the key in the command header of the write command may beunfixed, or may be a preset fixed location. If a location of the key inthe write command is unfixed, the write command may further carry keylocation information. The key location information may be a combinationof a key length and a key offset. The key offset describes a startlocation of the key in the write command. Alternatively, the keylocation information may be a combination of a start location of the keyin the write command and an end location of the key in the writecommand. If the start location of the key in the write command ispreset, the key location information may be a key length, and the keylength describes a length of the key.

There are two solutions of presetting the start location of the key. Onesolution is presetting the location of the key in the command. Forexample, the key starts at the 20^(th) bit counting from the first bitof the command. The other solution is presetting a relative locationbetween the key and another field. For example, a key field follows akey length field, and the key field and the key length field areadjacent. Similarly, all “preset” locations used in this embodiment andanother embodiment may be implemented by using the two solutions, forexample, start locations of the value and metadata that are subsequentlydescribed in this embodiment.

The length of the key may be fixed or variable. That the length of thekey is fixed means that key lengths in all commands are the same. Thatthe length of the key is variable means that key lengths in differentcommands may be different. When the length of the key is fixed, acommand receiver may ignore the location information (for example, thekey length), or the write command may not carry the locationinformation. After receiving the write command, the storage devicedirectly reads the key according to a preset start location andaccording to a fixed length.

A location of the value in the write command may be fixed, or may beunfixed. If a location of the value in the write command is unfixed, thewrite command may further carry value location information. The valuelocation information may be a value length. A start location of thevalue in the write command is preset, and therefore may not be carriedin the write command. The value may be read from the write command fromthe start location of the value and by using the value length as a readlength. The value location information may be a combination of the valuelength and a value offset. The value offset describes the start locationof the value in the write command. Alternatively, the value locationinformation may be a combination of the start location of the value inthe write command and an end location of the value in the write command.

The length of the value may be fixed or variable. When the length of thevalue is fixed, a command receiver may ignore the location information(for example, the value length), or the write command may not carry thelocation information. The command receiver directly reads the valueaccording to a preset start location and according to a fixed length.

Optionally, the write command further carries metadata of the value. Themetadata may be carried in the command header of the write command or inthe payload.

A location of the metadata in the write command may be fixed. If alocation of the metadata in the write command is unfixed, the writecommand may further carry metadata location information. The metadatalocation information is similar to the value location information.Therefore, reference may be made to the description of the valuelocation information. Details are not described herein again. Similarly,a length of the metadata may be fixed or variable.

Referring to FIG. 2 , FIG. 2 shows an optional command format of a writecommand, where a common header is a part of an NVMe command header. Thecommand carries two KVs, and therefore has two keys: a key 1 and a key2; two values: a value 1 and a value 2; two key lengths: a key 1 lengthand a key 2 length; and two value lengths: a value 1 length and a value2 length. In addition, the command further carries two pieces ofmetadata: metadata 1 and metadata 2; and a corresponding metadata length1 and a corresponding metadata length 2.

Referring to FIG. 3 , FIG. 3 is a schematic diagram of another NVMecommand format. Compared with FIG. 2 , FIG. 3 adds value locationinformation (a value 1 offset and a value 2 offset) and metadatalocation information (a metadata 1 offset, a metadata 1 length, ametadata 2 offset, and a metadata 2 length), and further adds the numberof KV. A command shown in FIG. 3 carries two KVs, and therefore a valueof the number of KV is 2. Location information in the NVMe commanddescribes a location of a field in the NVMe. Arrows used in FIG. 3indicate that a location of to-be-written data (for example, a startlocation) may be found by using an offset. For example, after the value1 offset field is read, a value of a value 1 offset field describes anoffset of a value 1 in the command, and therefore the value 1 offset maybe read. In the command format in FIG. 3 , distribution of fields isdetermined according to a field type. Fields of a same type are adjacentto each other. For example, both the value and the metadata belong toare data, and therefore are adjacent; both the value locationinformation and the metadata location information are locationinformation, and therefore are adjacent.

Referring to FIG. 4 , FIG. 4 is a schematic diagram of another NVMecommand format. Compared with those in FIG. 3 , fields are distributedaccording to a KV to which the fields belong, and fields of a same KVare adjacent. In the command format in FIG. 4 , a field of a KV 1 comesbefore a field of a KV 2. In addition, in the command format in FIG. 4 ,a value and a value length are adjacent, and metadata and a metadatalength are adjacent.

Referring to FIG. 5 , FIG. 5 is a schematic diagram of another NVMecommand format. In FIG. 5 , fields of a same KV are adjacent. Inaddition, the value length and the metadata length are adjacent, and thevalue and the metadata are adjacent.

12. An NVMe interface on the storage device receives the write command.The storage device obtains the key and the value from the write command.If the write command carries metadata, the storage device furtherobtains the metadata from the write command.

The storage device includes a controller and a storage medium. Thecontroller includes a processor, and optionally, may further include amemory. For example, the storage medium is a flash memory or a magneticdisk. Alternatively, the storage device may be a hard disk having amanagement capability, and is referred to as a smart hard disk.

If multiple NVMe command formats (for example, different NVMe commandformats are shown in FIG. 2 and FIG. 3 ) are supported by a same storagedevice, the storage device may determine a specific format of a receivedcommand by using a KV format ID. Then, the storage device reads contentsuch as a key or a value according to locations of fields such as thekey and the value in this format. For different NVMe command formats,location relationships of data may be different. For example, in someformats, a location of a key is fixed; in some formats, a location of akey is unfixed, and is determined by key location information.

If the write command carries one KV, the KV is read. If the writecommand carries at least two KVs, the at least two KVs are read. Thestorage device may learn a quantity of KVs by using a number of KVfield, and complete a read operation after reading a correspondingquantity of KVs. In addition to using the number of KV to identify aspecific case in which the read operation is completed, a terminator mayalso be added to the command. After the terminator is read, it indicatesthat all KVs in the command are read.

If the location of the key is fixed, the storage device reads the key byusing the fixed location. If the location of the key is unfixed, thestorage device reads the key from the write command according to the keylocation information. For example, the key location information is thekey length, and a start location of the key in the write command ispreset, and the storage device continuously reads data from the startlocation of the key and by using the key length as a read length, sothat the key carried in the write command may be obtained. For example,key location information is a combination of a key length and a keyoffset, the storage device continuously reads data by using the keyoffset as a start location of the key and by using the key length as aread length, so that the key carried in a write command may be obtained.For example, if the key location information is formed by a startlocation and an end location, the key may be obtained by reading databetween the start location and the end location.

For manners of reading the value and the metadata, refer to the mannerof reading the key. Details are not described herein again. When readingthe key/the value/the metadata, the storage device may further obtainthe key length/value length/metadata length.

Using the command format in FIG. 2 as an example, lengths of a commandheader field, a KV format ID field, a key length field, and a valuelength field are fixed, and a relative location of each field is alsofixed. Therefore, a start location of the key or value may not need tobe determined by using a field such a key offset or a value offset. Thestorage device reads fields of the write command in this order: readingthe command header; reading the KV format ID; reading the key 1 length;reading the key 1 according to a recorded value of the key 1 length;reading the value 1 length; reading the value 1 according to the value 1length; reading the key 2 length; reading the key 2 according to the key2 length; reading the value 2 length; and reading the value 2 accordingto the value 2 length.

13. The storage device stores the value. Specifically, a controller inthe storage device stores the key and the value in a non-volatilestorage medium. After receiving the value, the interface on the storagedevice first sends the value to a processor. In this step, the processortemporarily stores the value in a memory, and then delivers the value tothe non-volatile storage medium from the memory.

In addition, the storage device may further record a mappingrelationship between the key and the value storage space. The mappingrelationship may be stored in the storage medium in the storage device,or may be sent to a host and stored in the host. An example in which themapping relationship is stored in the storage device is used as anexample in the following.

If the write command further carries the metadata, the metadata is alsostored, and a mapping relationship between the key and metadata storagespace is recorded.

The value storage space may be described by using a start address of thevalue storage space and the value length. The metadata storage space mayinclude descriptions of a start address of the metadata storage spaceand the metadata data length. Referring to FIG. 6 , FIG. 6 is aschematic diagram of a mapping relationship, including a mapping betweenthe key and the start address of the value storage space, a mappingbetween the key and the value length, a mapping between the key and thestart address of the metadata storage space, and a mapping between thekey and the metadata length. A corresponding start address of the valuestorage space, a corresponding value length, a corresponding startaddress of the metadata storage space, and a corresponding metadatalength may be found in the mapping relationship by using the key as anindex. Content described in the schematic diagram shown in FIG. 6 isrecorded in a KV management unit. If the lengths of the value and themetadata are fixed, the value length and the metadata length areoptional.

The storage space may be a logical location or a physical location,provided that the controller in the storage device may read the valueand the metadata from the storage medium by using the storage space.

The process of writing a KV is described in step 11 to step 13. Next, aprocess of reading a KV is described in step 14 to step 16. The twoprocesses are independent of each other. The KV requested by a readcommand may be different from the KV written by using a write command.

14. A host generates an NVMe read command (hereinafter referred to as aread command for short), and sends the read command to the storagedevice. The read command carries the key. The key may be carried in acommand header of the read command.

The host generating the read command and the host generating the writecommand may be a same host, or may be different hosts. For a commandformat of the read command, refer to the format of the write command instep 11 and FIG. 2 . A read command includes a command header, a KVformat ID, and a key. Optionally, a read command carries key locationinformation. A read command may carry one key, or may carry at least twokeys. When carrying at least two keys, the read command may carry anumber of KV field, so as to describe a quantity of carried keys.

A read command may include neither a value field nor another fieldrelated to the value. In addition, a read command may include neither ametadata field nor another field related to the metadata.

15. The storage device receives the read command by using the NVMeinterface, and obtains the key from the read command; searches a KVmanagement unit stored in the storage device for value storage spacecorresponding to the key; and obtains the value from the value storagespace, constructs a response message of the read command, and sends theresponse message to the host. The response message carries the value.

Referring to step 12, according to different command formats, manners ofobtaining the key are slightly different. For example, the key may beobtained from a fixed location in the read command, or the key may beobtained from the write command according to location informationcarried in the read command.

Similarly, if the storage device stores metadata corresponding to thekey, metadata storage space may be searched for by using a similarmethod, so as to obtain the metadata.

It should be noted that if the KV management unit is stored in the host,the value storage space is searched for in the host by using the key. Avalue storage space address is sent to the storage device. The storagedevice obtains the value by using the value storage space, and sends thevalue to the host.

16. The host receives and stores the value. For example, the value maybe stored in a memory (for example, a cache) in the host, or stored in anon-volatile storage medium in the host.

In steps 11 to 16, both the value and the metadata are carried in theNVMe command, and conversion between a KV and a block is not required,thereby bringing about an advantage of being simple and quick. The readcommand does not need to carry a value LBA and/or a metadata LBA.Therefore, the value and/or the metadata can be read more quickly.

Referring to FIG. 7 , FIG. 7 shows an embodiment of a hardware topologyof a data processing system in the present disclosure. A host 71 and astorage device 72 communicate with each other. The host 71 includes aprocessor 711, a memory 712, and an interface 713. The storage device 72includes an interface 721, a controller 722, and a storage medium 723.The interface 713 and the interface 721 are connected by using acommunications link 73. For example, the communications link 73 is aPCIe bus, the Fibre Channel FC, or the Ethernet.

Operations performed by the host 71 may be performed by the processor711. For example, the processor 711 may perform steps 11, 14, and 16 byrunning a program in the memory 712. The memory 712 and the processor711 are relatively independent of each other, or may be integrated. Thestorage device 72 includes a control area 722 and a storage medium 723.Operations performed by the storage device 72 are performed by thecontroller 722 in the storage device. Specifically, a processor 7211 mayrun a program in a memory 7212 to perform the operations of the storagedevice. For example, the processor in the storage device is configuredto perform steps 12, 13, and 15. In some cases, for example, when theprocessor is an FPGA, there may be no memory, and the processor directlyperforms corresponding operations.

Similarly, same hardware is used in a subsequent method. A differencelies in that the host and the storage device are configured to performdifferent operations. For example, steps 21, 24, and 27 are performed bythe host 71, and steps 23 and 25 are performed by the storage device 72.In steps 22 and 26, some operations are performed by the host 71, andthe remaining operations are performed by the storage device 72.

Referring to FIG. 8 , the present disclosure further provides animplementation. A write command does not directly carry a value ormetadata, but the NVMe command carries a pointer. A to-be-written valueand/or to-be-written metadata may be obtained by using storage spacethat is pointed to by the pointer. Alternatively, a multi-level pointermanner is used. A pointer points to another pointer, and theto-be-written value and/or the to-be-written metadata are/is obtainedfrom storage space that is pointed to by the another pointer. Thisimplementation imposes no limitation on a size of the to-be-writtenvalue and/or a size of the to-be-written metadata.

A host and a storage device may be connected by using an IP network, anFC network, or the like, and may run on a Fabric architecture, which isalso referred to as an NOF (NVMe Over Fabric) architecture. In the NOFarchitecture, the storage device may obtain the value and/or themetadata in a remote direct memory access (RDMA) manner. If the storagedevice is inside the host, the storage device may further obtain thevalue and/or the metadata from the host in a direct memory access (DMA)manner. Similarly, the host may also directly obtain a value and/ormetadata from the storage device in the RDMA/DMA manner.

Step 21: A host constructs a write command. The write command carries aKV. The KV includes a value pointer and a key of a value. The writecommand is sent to an NVMe storage device by using an NVMe interface onthe host. The key and the value belong to a same KV pair.

The value pointer may be carried in a payload, or may be carried in acommand header. Similarly, other data carried in a write command or aread command may be carried in a command header, or may be carried in apayload.

In another embodiment, a write command may also carry a key pointerinstead of carrying a key. A principle of a obtaining the key accordingto the key pointer is the same as a principle of obtaining the value byusing the value pointer. Therefore, details are not described in thefollowing. Descriptions are merely made by using an example in which thewrite command carries the key.

The value pointer directly or indirectly points to value storage space(hereinafter also referred to as first storage space for ease ofdescription), and therefore the value may be obtained by using the valuepointer. When the value pointer points to the value storage space (thiscase is also considered as that the value pointer points to the value),the value may be obtained from the storage space that is pointed to bythe value pointer. Another case is as follows: The value pointer pointsto a first pointer; and the first pointer points to the value storagespace. The first pointer is found according to the value pointer, andthe value may be obtained from the storage space that is pointed to bythe first pointer. In the latter case, a value with a larger size may becarried. In another embodiment, reference between pointers may furtherhave more levels, provided that the value storage space can be foundfinally. For example, the value pointer points to the first pointer, thefirst pointer points to an A1^(th) pointer, the A1^(th) pointer pointsto an A2^(th) pointer, . . . , an (AN−1)^(th) pointer points to anAN^(th) pointer, and the AN^(th) pointer points to the value storagespace. N is an integer greater than or equal to 2. The value pointer maybe carried in the command header of the write command or in the payload.

The first storage space may be described by using a start address of thefirst storage space and the value length, or may be described by usingthe start address and an end address that are of the first storagespace. For example, the value pointer records the start address of thefirst storage space and the value length. Alternatively, the valuepointer points to another pointer, and the another pointer records thestart address of the first storage space and the value length. The firststorage space may be a logical location or a physical location, providedthat the storage device may read stored data from the storage medium byusing the first storage space.

Optionally, if the write command carries more than one KV, the writecommand further carries a number of KV, so as to describe a quantity ofKVs.

Optionally, the write command further carries a KV format ID. NVMecommands for transmitting a KV may be in multiple command formats. Fordifferent command formats, fields may be different, and locations of thefields may also be different. The KV format ID indicates a commandformat used by this command.

A location of the key in the command header of the write command may beunfixed, or may be a preset fixed location. For a feature of the key,refer to the description of the key in step 11. Details are notdescribed herein again.

Optionally, the write command further carries a metadata pointer.Similar to the value pointer, the metadata pointer directly orindirectly points to metadata storage space. Therefore, metadata may beobtained by using the metadata pointer. The metadata pointer may becarried in the command header of the write command or in the payload.

Because metadata pointer directly or indirectly points to the metadatastorage space, the metadata may be obtained by using the metadatapointer. When the metadata pointer directly points to the metadata(specifically, to the metadata storage space), the metadata may beobtained from the storage space that is pointed to by the metadatapointer. Another case is as follows: The metadata pointer points to asecond pointer, and the second pointer points to the metadata storagespace. The second pointer is found according to the metadata pointer;and the metadata may be obtained from the storage space that is pointedto by the second pointer. In the latter case, metadata with a largersize may be carried. In another embodiment, reference between pointersmay further have more levels, provided that the metadata storage spacecan be found finally. For example, the metadata pointer points to thesecond pointer, the second pointer points to a B1^(th) pointer, theB1^(th) pointer points to a B2^(th) pointer, . . . , a (BN−1)^(th)pointer points to a BN^(th) pointer, and the BN^(th) pointer points tothe metadata storage space. N is an integer greater than or equal to 2.

In addition, the metadata may be transmitted without using the pointer,but be directly carried in the command. For details, refer to step 11and the manners of carrying the metadata in FIG. 2 and FIG. 3 .

The value pointer may be a data pointer (DPTR). The metadata pointer maybe a metadata pointer (MPTR).

Referring to FIG. 9 , FIG. 9 is a diagram of a command format. A commandin FIG. 9 carries two KVs. A key in the KV is directly carried in awrite command. A value is carried in the write command in a pointermanner. There are a key 1 and a DPTR 1 (pointing to a value 1), and akey 2 and a DPTR 2 (pointing to a value 2). In addition, metadata of thetwo KVs is further carried in a pointer manner. An MPTR 1 points tometadata 1, and an MPTR 2 points to metadata 2. In this embodiment ofthe present disclosure, each command may carry one KV, or may carry atleast two KVs.

Referring to FIG. 10 , FIG. 10 is a diagram of another command format. Apointer (DPTR or MPTR) in a command does not directly point to a valueor metadata, but points to a PRP entry or an SGL entry. The PRP entry orthe SGL entry is a node in a linked list. Each PRP/SGL entry points toanother address. A value or metadata is stored in the address that ispointed to by the PRP/SGL entry. That is, a write command points to avalue or metadata in a second-level pointer manner. In the solution inFIG. 10 , a key is carried in a command, and specifically, is carried ina command header.

Referring to FIG. 11 , a difference between a command format in FIG. 11and the command format in FIG. 10 is as follows: A key in FIG. 11 is notdirectly carried in a command, but transmitted in a pointer manner. Fora specific carrying manner, refer to the description of the valuepointer. A key pointer may be carried in the command header of thecommand.

Specifically, a DPTR points to a PRP/SGL entry 1, and a PRP/SGL entry 2and the PRP/SGL entry 1 belong to a same linked list. Therefore, whenthe PRP/SGL entry 1 is found, the PRP/SGL entry 2 may be found.Therefore, it may be considered that the DPTR points to the PRP/SGLentry 1 and the PRP/SGL entry 2. The PRP/SGL entry 1 points to a value1, and the PRP/SGL entry 2 points to a value 2. Similarly, an MPTRpoints to a PRP/SGL entry 3 and a PRP/SGL entry 4; the PRP/SGL entry 3points to metadata 1; and the PRP/SGL entry 4 points to metadata 2.Value 1 storage space and value 2 storage space may be found by usingthe DPTR. Metadata 1 storage space and metadata 2 storage space may befound by using the MPTR. Both the PRP entry and the SGL entry are nodesin the linked list. The PRP is applicable to the ordinary NVMe (a hostand a storage device are connected by using the PCIe), and the SGL isapplicable to the NOF (a host and a storage device are connected byusing the Fabric). The PRP may be used in RDMA, and the PRP or the SGLmay be used in DMA.

The PRP transmits a location in which the data is located to an NVMedevice by using a series of pointers pointing to a memory page. Afterreceiving the addresses, the NVMe device may read the data from the hostinto the NVMe device in the DMA manner. Compared with the PRP, an SGLtransmission mechanism is more flexible. A transmission data amount maybe specified, and some address spaces can be skipped during a continuousaddress transmission process. The SGL transmits, to the NVMe device, anaddress of data that needs to be transmitted. After receiving theaddress, the NVMe device reads the data from the host into the NVMedevice in the DMA manner.

In addition, compared with FIG. 9 , FIG. 10 further adds a number of KVfield and a key length field, which are already described in step 11 andstep 12. Details are not described again.

Step 22: The storage device receives the write command by using an NVMeinterface. The storage device obtains a value length by using the valuepointer, allocates storage space (hereinafter also referred to as secondstorage space for ease of description) to the value according to thevalue length, and sends location information of the allocated storagespace to the host. The storage device sends a transmission request(e.g., a first transmission request) to the host, and obtains the valuefrom first storage space in the host. If the host and the storage deviceare connected by using the PCIe, the first transmission request may be aDMA transmission request, for example, a single DMA transmissionrequest. If the host and the storage device are connected by using theFabric, the first transmission request may be an RDMA transmissionrequest, for example, a single RDMA transmission request. The firsttransmission request uses an address of the first storage space as anaccess address, and uses an address of the second storage space as awrite address. In the first transmission request, the access address maybe: a start address of the first storage space and the value length; andthe write address may be: a start address of the second storage space(or a start address of the second storage space and the value length).

The storage device sends the DMA/RDMA transmission request to the host.After receiving the transmission request, the host performs DMA/RDMAtransmission and sends the value to the storage device.

Pre-allocating the second storage space is optional. Alternatively, thestorage device may not allocate the second storage space in advance, butdirectly obtains the value from the host, and then allocates the secondstorage space to the value. In this case, the first transmission requestcarries no write address.

If the write command carries a metadata pointer, storage space (e.g., afourth storage space) is further allocated to metadata. Because a mannerof processing the metadata pointer is similar to that of the valuepointer, only the value pointer is described subsequently.

Before the value is obtained according to the value pointer, storagespace (e.g., the second storage space) used to store the value isallocated in the storage device according to the value length. Thesecond storage space is not less than the value length. The secondstorage space may be described by using the start address and an endaddress, may be described by using the start address and the valuelength, or may be described by using only the start address. The valuelength may be determined by the value storage space. For example, in thewrite command, the first storage space is described by using the startaddress of the space in which the value is stored and the value length,so that the value length may be directly obtained from the writecommand.

The storage device includes a controller and a storage medium. Thecontroller includes a processor. For example, the storage medium is aflash memory or a magnetic disk.

A command header field, a KV format ID field, a key field, or a keylength field are already described in step 12. Details about obtainingthe fields and using the fields to obtain corresponding information arenot described herein again.

Different from the embodiments described in steps 11 to 16, in thisembodiment, the value and/or metadata are/is not directly obtained fromthe command. Instead, the value and/or metadata are/is obtained by usinga pointer.

The value pointer carried in the write command directly points to thefirst storage space. For example, in the command format in FIG. 9 , thepointer DPTR in the write command points to the value storage space(e.g., the first storage space). Specifically, the pointer DPTR pointsto a memory address range in the host, and the value is stored in thememory address range. The value is obtained from a host memory addressaccording to the storage space described by the DPTR and in the DMA orRDMA manner. The metadata may be obtained in the same manner by usingthe MPTR.

If the value pointer in the write command indirectly points to thevalue, reference may be made to the format of the write command in FIG.10 : The value pointer directly points to another pointer, and theanother pointer points to the value. The pointer DPTR in the writecommand points to the PRP/SGL entry; the PRP/SGL entry points to thehost memory address; and the host memory address is the value storagespace. The storage device first finds the PRP/SGL entry by using theDPTR; then finds, by using the PRP/SGL entry, the value storage spacelocated in a host memory; and obtains the value from the host memory inthe DMA or RDMA manner.

If the metadata pointer is carried in the write command, a manner ofobtaining the metadata is the same as the manner of obtaining the value.If the metadata is directly carried in the write command, the metadatamay be directly obtained from the write command by referring to step 12.

The storage device sends the first transmission request to the host, andobtains the value from the first storage space in the host. If the hostand the storage device are connected by using the PCIe, the firsttransmission request may be the DMA transmission request. If the hostand the storage device are connected by using the Fabric, the firsttransmission request may be the RDMA transmission request. Specifically,there may be two steps. (1) The storage device sends a transmissionrequest to the host. The transmission request carries the first storagespace as an access address, and carries the second storage space as awrite address. Specifically, the first storage space carried in thetransmission request may be described by using the start address of thefirst storage space and the value length; and the second storage spacemay be described by using the start address of the second storage space.(2) After receiving the transmission request, the host reads data fromthe first storage space, and sends the data to the second storage spacein the storage device for storage.

In this step, the key, the value, and the metadata may be transmitted bymeans of a single DMA/RDMA transmission. Alternatively, the key, thevalue, and the metadata may be separately transmitted.

Step 23: The storage device stores the value. Specifically, a controllerin the storage device stores the key and the value in a storage mediumin the storage device. If the metadata is further obtained in step 22,the metadata is also stored.

For example, the value is stored in the storage medium in the storagedevice in a consecutive manner from the start address of the secondstorage space.

In addition, a mapping relationship between the key and the valuestorage space may be further recorded. Referring to FIG. 6 , the valuestorage space in FIG. 6 is described by using the start address and thevalue length. The mapping relationship is recorded in a KV managementunit. The value length and the metadata length are optional, becauseboth the value and the metadata may have fixed lengths.

In steps 21 to 23, the value is transmitted in the pointer manner. Inanother embodiment, the key may also be transmitted in the pointer(e.g., a direct pointer or an indirect pointer) manner. For details,refer to the transmission manner of the value. Details are not describedherein again.

The process of a write command is described in steps 21 to 23, and anexecution process of a read command is described in steps 24 to 26. Thetwo processes are independent of each other. The KV requested by a readcommand may be different from the KV written by using a write command.Command formats of a read command and a write command are similar, but adifference lies in that a read command carries neither a value pointernor a metadata pointer.

24. A host generates a read command, and sends the read command to thestorage device. The read command carries the key. The key may be carriedin a command header of the read command.

The host generating the read command and the host generating the writecommand may be a same host, or may be different hosts. For a format ofthe read command, refer to the format of the write command in step 11and FIG. 2 . A read command includes a command header, a KV format ID,and a key. Optionally, a read command carries a key or a key pointer. Aread command may carry one key, or may carry at least two keys. Whencarrying at least two keys, the read command may carry a number of KVfield, so as to describe a quantity of carried keys.

The read command is used to request to read the value and/or themetadata.

Compared with the write command, the read command may include neither avalue field nor value location information, and the read command mayinclude neither a metadata field nor metadata location information.

25. The storage device receives the read command by using the NVMeinterface, and obtains the key from the read command. The storage devicesearches, by using the obtained key, the mapping relationship stored inthe storage device for the value storage space, and sends the valuestorage space to the host. The value storage space in the storage deviceis the second storage space.

If the key is directly carried in the read command, referring to FIG. 12, according to different command formats, manners of obtaining the keyfrom the read command are slightly different. For example, the key maybe obtained from a fixed location in the read command; or if a locationof the key in the read command is unfixed, the key may be obtained fromthe read command according to location information carried in the readcommand.

Optionally, if the storage device stores metadata corresponding to thekey, metadata storage space may be further obtained and sent to thehost.

26. The host allocates storage space (e.g., named third storage space)to the value according to the value length. The host constructs atransmission request (e.g., a second transmission request), sends thetransmission request to the storage device, and obtains the value fromthe second storage space in the storage device.

If the host and the storage device are connected by using the PCIe, thesecond transmission request may be a DMA transmission request, forexample, a single DMA transmission request; if the host and the storagedevice are connected by using the Fabric, the second transmissionrequest may be an RDMA transmission request, for example, a single RDMAtransmission request. In the transmission request, the access addressmay be: the start address of the second storage space and the valuelength; and the write address may be the start address of the thirdstorage space (or the start address of the third storage space and thevalue length). It may be learned from the foregoing steps that thesecond storage space is used to store the value, and therefore the valuelength is the same as a size of the second storage space. That is, thesize of the second storage space is equal to a size of the third storagespace.

The value length may be determined by the value storage space. Forexample, in the read command, the second storage space is described byusing the start address of the space in which the value is stored andthe value length, so that the value length may be directly obtained fromthe read command.

The host sends the DMA/RDMA transmission request to the storage device.After receiving the transmission request, the storage device performsDMA/RDMA transmission and sends the value to the host.

Pre-allocating the third storage space is optional. Alternatively, thehost may not pre-allocate the third storage space, but directly obtainsthe value from the storage device, and then allocates the third storagespace to the value. In this case, the transmission request carries nowrite address.

Similarly, the host may allocate storage space to the metadata accordingto the metadata length, and obtains the metadata from the storagedevice.

27. The host stores the received value in the third storage space. Forexample, the value is stored in the host in a consecutive manner from astart address of the third storage space. For example, the third storagespace is in a memory in the host.

The metadata is stored in the host by using a method similar to themethod for storing the value in the host.

It should be noted that in another embodiment, DMA or RDMA may not beused, and steps 26 and 27 are modified as follows: The host allocatesstorage space to the value; and the storage device reads the value fromthe second storage space, and writes the read value into the thirdstorage space.

In addition, another optional solution of step 26 is as follows: theNVMe read command that is received by the NVMe storage device and thatis sent by the host may further carry free space information of thehost. The free space information is used to describe a size of acontiguous free storage space in the host. After the NVMe storage devicereceives the NVMe read command from the host, the process furtherincludes the following steps: The NVMe storage device determines whetherfree storage space in the host is greater than or equal to the secondstorage space. If the free storage space in the host is greater than orequal to the second storage space, perform the step of sending thelocation information of the second storage space to the host, or if thefree storage space in the host is not greater than or equal to thesecond storage space, end the step. In this solution, the contiguousfree storage space in the host may be referred to as third storagespace.

Referring to FIG. 12 , step 21 to step 23 are described by using anexample in which a value pointer and a metadata pointer are carried in asame command.

Step 31: A host constructs a write command. The write command carries akey. In addition, the write command carries a value source addresslinked list and a metadata source address linked list. The sourceaddress linked list has a function of a pointer. The value sourceaddress linked list and the metadata source address linked listrespectively point to value storage space and metadata storage space.

Step 32: The host sends the write command to an NVMe device.

Step 33: After receiving the write command, the NVMe device parses outthe value source address linked list and the metadata source addresslinked list from the write command. For example, the linked list is aPRP entry or an SGL entry.

Step 34: The NVMe device parses out a value length from the value sourceaddress linked list, and parses out a metadata length from the metadatasource address linked list. The source address linked lists describestorage space of to-be-read data, and therefore the value length and themetadata length may be parsed out from the source address linked lists.

Step 35: The NVMe device sends a DMA or an RDMA request to the host. Therequest carries the value source address linked list, the metadatasource address linked list, a value destination address linked list, anda metadata destination address linked list. The value destinationaddress linked list describes storage space that is reserved by the NVMedevice and that is used to store the value. The metadata destinationaddress linked list describes storage space that is reserved by the NVMedevice and that is used to store the metadata.

Step 36: After receiving the DMA/RDMA request, the host sends the key tothe NVMe device according to a source address and a destination addressin step 35.

Step 37: The NVMe device stores the value and the metadata in a medium.

Step 38: The NVMe device records the value storage space and themetadata storage space. A mapping between the storage space and the keyis established, so that the key is subsequently used to search for thevalue storage space and the metadata storage space. The mappingrelationship may be stored in a KV management unit. The KV managementunit may further record the value length and the metadata length.

In the foregoing steps, the key is directly carried in the command. Inanother implementation, the command may carry a key pointer instead ofcarrying a key. After receiving the command, the storage device obtainsthe key according to the key pointer. For a specific step of obtainingthe key, refer to the process of obtaining the value in step 22. Becauseprinciples are similar, details are not described herein again.

Referring to FIG. 13 , step 24 to step 27 are described in detail byusing an example in which a value pointer and a metadata pointer arecarried in a same command.

Step 41: A host constructs a read command, where the read commandcarries a key.

Step 42: The host sends, to an NVMe device, the read command thatcarries the key.

Step 43: The NVMe device searches a KV management unit for a valuelength and a metadata length that are corresponding to the key. The KVmanagement unit records value storage space and metadata storage space.

Using the value storage space as an example, the value is stored in theNVMe device. The value storage space is described by using a value startaddress and a value end address, or the start address and the valuelength. Therefore, after the value storage space is obtained, the valuelength may be obtained. Similarly, the metadata length may be obtained.

Step 44: The NVMe device sends a response message to the host, where theresponse message carries the value length and the metadata length.

Step 45: The host allocates, according to the value length and themetadata length, storage space to a value and metadata for subsequentlystoring the value and the metadata.

Step 46: The host sends a DMA/an RDMA request to the NVMe device. Therequest carries a source address and a destination address of a currenttransmission. The source address is the value storage space and themetadata storage space in the NVMe. The destination address is thestorage space reserved by the host for the value, and the storage spacereserved for the metadata.

Step 47: After receiving the DMA/RDMA request sent by the host, the NVMedevice sends the value and the metadata according to the DMA/RDMAprotocol.

Step 48: The host receives the value and the metadata.

Step 49: The host stores the received value and metadata. For example,the host stores the received value and metadata in a host memory.

DMA or RDMA is generally used for reading data of a contiguous addressspace. When the storage space in which the value in stored and thestorage space in which the metadata is stored are noncontiguous, twoDMA/RDMA transmissions may be performed.

Referring to FIG. 14A and FIG. 14B, the present disclosure furtherprovides an embodiment based on steps 21 to 23, so as to improve theembodiment based on FIG. 12 . The improvement lies in that a key, avalue, and metadata in a same command are separately obtained byperforming three DMA/RDMA transmissions.

Optionally, if any one of the transmissions fails, it means that the KVtransmission is unsuccessful, and consequently, data that issuccessfully transmitted may be deleted, an error code is uploaded, andsubsequent data transmission is canceled. In addition, storage spacepreviously allocated to a KV (a key, a value, and metadata) may bereleased.

Step 51: Construct an NVMe write command.

The write command carries a key. In addition, the write command carriesa value source address linked list and a metadata source address linkedlist. The source address linked list has a function of a pointer. Thevalue source address linked list and the metadata source address linkedlist respectively point to value storage space and metadata storagespace.

Step 52: A host sends the write command to an NVMe device.

Step 53: After receiving the write command, the NVMe device parses out avalue source address linked list and a metadata source address linkedlist from the write command. For example, the linked list is a PRP entryor an SGL entry.

Step 54: The NVMe device parses out a key length from a key sourceaddress linked list, parses out a value length from the value sourceaddress linked list, parses out a metadata length from the metadatasource address linked list, and reserves storage space for the key, thevalue, and the metadata. The source address linked lists describestorage space of to-be-read data, and therefore the value length and themetadata length may be parsed out from the source address linked lists.

Step 55: The NVMe device sends a DMA/an RDMA request to the host. Therequest carries the key source address linked list and a key destinationaddress linked list. The key destination address linked list describesthe storage space that is reserved by the NVMe device and that is usedto store the key.

Step 56: After receiving the DMA/RDMA request, the host sends the key tothe NVMe device according to a source address and a destination addressin step 55.

Step 57: If the key fails to be transmitted, the NVMe device cancelssubsequent transmission of the value and metadata; optionally, releasesthe storage space reserved for the key, the value, and the metadata; andreports an error code to the host. If the key is successfullytransmitted, proceed to subsequent step 58.

Step 58: The NVMe device sends a DMA/an RDMA request to the host. Therequest carries the value source address linked list and a valuedestination address linked list. The value destination address linkedlist describes the storage space that is reserved by the NVMe device andthat is used to store the value.

Step 59: After receiving the DMA/RDMA request, the host sends the valueto the NVMe device according to a source address and a destinationaddress in step 58.

Step 60: If the value fails to be transmitted, the NVMe device cancelssubsequent transmission of metadata; optionally, releases the storagespace reserved for the value and the metadata; optionally, deletes thetransmitted key; and reports an error code to the host. If the value issuccessfully transmitted, proceed to subsequent step 61.

Step 61: The NVMe device sends a DMA/an RDMA request to the host. Therequest carries the metadata source address linked list and a metadatadestination address linked list. The metadata destination address linkedlist describes the storage space that is reserved by the NVMe device andthat is used to store the metadata.

Step 62: After receiving the DMA/RDMA request, the host sends themetadata to the NVMe device according to a source address and adestination address in step 61.

Step 63: If the metadata fails to be transmitted, optionally, releasethe storage space reserved for the metadata; optionally, delete thetransmitted key and value; and report an error code to the host. If themetadata is successfully transmitted, proceed to subsequent step 64.

Step 64: Store the value and the metadata in the storage device. Thevalue and the metadata that are obtained in steps 60 and 63 are in amemory. In this step, the value and the metadata are stored in anon-volatile medium, for example, a hard disk on the NVMe device.

Step 65: Record the value storage space and the metadata storage space.

It may be learned from step 55 to step 63 in FIG. 14A and FIG. 14B thatthe key, the value, and the metadata are respectively obtained by meansof different DMA transmissions. If any of the data items fails to betransmitted, transmission of remaining data is canceled, andsuccessfully transmitted data may be deleted. The remaining steps inFIG. 14A and FIG. 14B are similar to those in FIG. 12 , and are alreadydescribed earlier. Details are not described herein again.

Similarly, the value and the metadata may be separately transmitted, andin addition, the value (or the metadata) may also be separatelytransmitted for multiple times, for example, one value is separatelytransmitted by performing at least two DMA/RDMA transmissions. If anytransmission fails, it is determined that the overall KV transmissionfails, and the storage space reserved for the key, the value, and themetadata are released. When the NVMe storage device and the host areconnected by using a PCIe bus, the storage device sends at least two DMAtransmission requests to the host to obtain the value. A part of thevalue is obtained during each DMA transmission. When the NVMe storagedevice and the host are connected by using the Fabric, the storagedevice sends at least two RDMA transmission requests to the host toobtain the value. A part of the value is obtained during each RDMAtransmission.

The solution in which the value (or the metadata) is separatelytransmitted for multiple times and the solution in which the value andthe metadata are separately transmitted and that is described in step 55to step 63 may be combined for use. In this case, if any transmissionfails (or a transmission request fails to be executed), it is determinedthat the overall KV transmission fails, and the storage space reservedfor the key, the value, and the metadata are released.

A process in FIG. 14A and FIG. 14B describes a manner of processing awrite command. An initiator of a DMA/an RDMA transmission request is anNVMe device. Similarly, a similar solution may also be used in a processof processing a read command, and a key, a value, and metadata arerespectively obtained by means of different DMA transmissions. Adifference lies in that an initiator of a transmission request is ahost, and the NVMe device transmits the key, the value, and the metadataby means of DMA/RDMA.

Referring to FIG. 15 , the present disclosure provides a data processingsystem, including a host apparatus 80 and a storage apparatus 90. Thehost apparatus 80 and the storage apparatus 90 are connected by usingthe PCIe or the Fabric. The host apparatus 80 may read KV data from orwrite KV data into the storage apparatus 90.

The host apparatus 80 may be a physical device or a logical apparatus,and includes a transceiver module 801, a management module 802, and acache module 803. The storage apparatus 90 may be a physical device or alogical apparatus, and includes an interface module 901, a processingmodule 902, and a storage module 903. The transceiver module 801 and theinterface module 901 communicate with each other. The host apparatus 80has functions of the foregoing host, and the storage apparatus 90 hasfunctions of the foregoing storage device.

The following briefly describes functions of the host apparatus 80 andthe storage apparatus 90. It should be noted that because the functionsof the two apparatuses (and corresponding modules) are described indetail in the method process, only a brief description is given herein.

The storage apparatus 90 includes the interface module 901, theprocessing module 902, and the storage module 903. The interface module901 is configured to receive an NVMe write command sent by a host, wherethe NVMe write command carries a key, the NVMe write command carries avalue pointer, the value pointer points to first storage space in thehost, the first storage space is used to store a value, and the key andthe value belong to a same KV pair. The processing module 902 isconfigured to: obtain the key from the NVMe write command, obtain avalue length according to the value pointer, and allocate second storagespace to the value according to the value length. The storage module 903is configured to: send a first transmission request to the host, obtainthe value from the host, and store the value in the second storagespace. The second storage space may be provided by a storage medium inthe NVMe storage device. The storage medium is connected to a processorin the NVMe storage device. Based on this solution, in a process oftransmitting KV data from the host to the NVMe storage device, the KVdata does not need to be converted into a block form, so that KV datastorage efficiency is improved.

Alternatively, the storage apparatus 90 includes the interface module901, the processing module 902, and the storage module 903. Theinterface module 901 is configured to receive an NVMe write command,where a header of the NVMe write command carries a key key, the NVMecommand further carries a value value, the key is corresponding to thevalue, and the key and the value belong to a same KV pair. Theprocessing module 902 is configured to obtain the key and the value fromthe NVMe write command. The storage module 903 is configured to storethe value in the storage medium in the NVMe storage device.

In an implementation, the host apparatus 80 includes the transceivermodule 801, the management module 802, and the cache module 803. Thetransceiver module 801 is configured to send an NVMe read command to thestorage apparatus 90, where the NVMe command carries a key. Thetransceiver module 801 is further configured to receive a responsemessage of the NVMe read command from the NVMe storage device, where theresponse message carries location information of the second storagespace. The management module 802 is configured to reserve third storagespace for the value according to a value length in the value locationinformation. The transceiver module 801 is further configured to: send atransmission request to the NVMe storage device, where an access addressof the transmission request is the second storage space, and obtain thevalue from the NVMe storage device. The cache module 803 stores thevalue in the third storage space in the host apparatus 80. Based on thismodule structure, the host apparatus may read the value and the metadatain the storage apparatus.

In combination with the examples described in the embodiments disclosedin this specification, units and algorithm steps may be implemented byelectronic hardware or a combination of computer software and electronichardware. Whether the functions are performed by hardware or softwaredepends on particular applications and design constraint conditions ofthe technical solutions. A person skilled in the art may use differentmethods to implement the described functions for each particularapplication, but it should not be considered that the implementationgoes beyond the scope of the present disclosure.

The foregoing descriptions are merely specific implementations of thepresent invention, but are not intended to limit the protection scope ofthe present invention. Any variation or replacement based on the presentinvention shall fall within the protection scope of the presentinvention. Therefore, the protection scope of the present inventionshall be subject to the protection scope of the claims.

What is claimed is:
 1. A data processing method implemented by anon-volatile memory express (NVMe) storage device, the methodcomprising: receiving an NVMe command sent by a host, wherein the NVMecommand indicates to store a value in the NVMe storage device, the NVMecommand carries a key (K) and a value (V) identifier of the value, andthe key and the value belong to the same key value pair; obtaining thevalue based on the value identifier; and storing the value in the NVMestorage device.
 2. The data processing method of claim 1, wherein thevalue identifier comprises a pointer of the value and the pointerindicates a storage location of the value, and wherein obtaining, basedon the value identifier, the value comprises: obtaining the value basedon the pointer of the value.
 3. The data processing method of claim 2,wherein the value identifier further comprises a length of the value,and the storing the value in the NVMe storage device comprises:identifying a storage space for the value according to the value lengthin the NVMe storage device; and storing the value in the storage spacein the NVMe storage device.
 4. The data processing method of claim 1,wherein the value identifier comprises the value, and wherein obtaining,based on the value identifier, the value comprises: obtaining valuebased on the NVMe command.
 5. The data processing method of claim 4,wherein the value identifier further comprises a length of the value,and the storing the value in the NVMe storage device comprises:identifying a storage space for the value according to the value lengthin the NVMe storage device; and storing the value in the storage spacein the NVMe storage device.
 6. The data processing method of claim 1,wherein the method further comprises: recording a correspondence betweenK and V in a KV mapping relationship in the NVMe storage device, whereinthe correspondence between K and V comprises a matching relationshipbetween K and V.
 7. A data processing method implemented by anon-volatile memory express (NVMe) storage device, the methodcomprising: receiving an NVMe command sent by a host, wherein the NVMecommand indicates to read a value in the NVMe storage device, the NVMecommand carries a key and a value identifier of the value, and the keyand the value belong to the same key value pair; obtaining the valuebased on the value identifier; and sending the value to the host.
 8. Thedata processing method of claim 7, wherein the value identifier of thevalue comprises a pointer of the value, and wherein the obtaining, basedon the value identifier, the value comprises: obtaining the value basedon the pointer.
 9. A non-volatile memory express (NVMe) storage device,comprising a controller and a storage medium, wherein the controller isconnected to the storage medium, and the storage medium is configured toprovide storage space, wherein the controller is configured to: receivean NVMe command sent by a host, wherein the NVMe command indicates tostore a value in the NVMe storage device, the NVMe command carries a key(K) and a value (V) identifier of the value, and the key and the valuebelong to the same key value pair; obtain the value based on the valueidentifier; and store the value in the NVMe storage device.
 10. The NVMestorage device of claim 9, wherein the value identifier comprises apointer of the value and the pointer indicates a storage location of thevalue and the controller is configured to: obtain the value based on thepointer of the value.
 11. The NVMe storage device of claim 10, whereinthe value identifier further comprises a length of the value and thecontroller is configured to: identify a storage space for the valueaccording to the value length in the NVMe storage device; and store thevalue in the storage space in the NVMe storage device.
 12. The NVMestorage device of claim 9, wherein the value identifier comprises thevalue and the controller is configured to: obtain the value based on theNVMe command.
 13. The NVMe storage device of claim 12, wherein the valueidentifier further comprises a length of the value and the controller isconfigured to: identify a storage space for the value according to thevalue length in the NVMe storage device; and store the value in thestorage space in the NVMe storage device.
 14. The NVMe storage device ofclaim 13, wherein the controller is configured to: record acorrespondence between K and V in a KV mapping relationship in the NVMestorage device, wherein the correspondence between K and V comprises amatching relationship between K and V.
 15. A non-volatile memory express(NVMe) storage device, comprising a controller and a storage medium,wherein the controller is connected to the storage medium, and thestorage medium is configured to provide storage space, wherein thecontroller is configured to: receive an NVMe command sent by a host,wherein the NVMe command indicates to read a value in the NVMe storagedevice, the NVMe command carries a key and a value identifier of thevalue, and the key and the value belong to the same key value pair;obtain, based on the value identifier, the value; and send the value tothe host.
 16. The NVMe storage device of claim 15, wherein the valueidentifier of the value comprises a pointer of the value, and thecontroller is configured to: obtain, based on the pointer, the value.17. A storage system, wherein the system comprises a host and anon-volatile memory express (NVMe) storage device, wherein the NVMestorage device comprises a controller and a storage medium, wherein thecontroller is connected to the storage medium, and the storage medium isconfigured to provide storage space, wherein: the host is configured tosend a NVMe command, wherein the NVMe command indicates to store a valuein the NVMe storage device, the NVMe command carries a key (K) and avalue (V) identifier of the value, and the key and the value belong tothe same key value pair; and the controller is configured to receive theNVMe command, obtain the value based on the value identifier, and storethe value in the NVMe storage device.
 18. The storage system of claim17, wherein the value identifier comprises a pointer of the value andthe pointer indicates a storage location of the value, and thecontroller is further configured to obtain the value based on thepointer of the value.
 19. The storage system of claim 18, wherein thevalue identifier further comprises a length of the value, and thecontroller is further configured to identify a storage space for thevalue based on the value length in the NVMe storage device, and storethe value in the storage space in the NVMe storage device.
 20. Thestorage system of claim 17, wherein the value identifier comprises thevalue, the controller is further configured to obtain value based on theNVMe command.
 21. The storage system of claim 20, wherein the valueidentifier further comprises a length of the value, and the controlleris further configured to identify a storage space for the value based onthe value length in the NVMe storage device; and store the value in thestorage space in the NVMe storage device.
 22. The storage system ofclaim 17, wherein: the controller is further configured to record acorrespondence between K and V in a KV mapping relationship in the NVMestorage device, and the correspondence between K and V comprises amatching relationship between K and V.
 23. The storage system of claim17, wherein the controller is further configured to: receive an NVMecommand sent by a host, wherein the NVMe command indicates to read avalue in the NVMe storage device, the NVMe command carries a key and avalue identifier of the value, and the key and the value belong to thesame key value pair; obtain, based on the value identifier, the value;and send the value to the host.
 24. The storage system of claim 17,wherein the value identifier of the value comprises a pointer of thevalue, and the controller is further configured to obtain the valuebased on the pointer.
 25. A non-transitory computer-readable storagemedium comprising instructions that, responsive to being executed by acomputer, cause the computer to: receive an NVMe command sent by a host,wherein the NVMe command indicates to store a value in the NVMe storagedevice, the NVMe command carries a key (K) and a value (V) identifier ofthe value, and the key and the value belong to the same key value pair;obtain the value based on the value identifier; and store the value inthe NVMe storage device.
 26. A non-transitory computer-readable storagemedium comprising instructions that, responsive to being executed by acomputer, cause the computer to: receive an NVMe command sent by a host,wherein the NVMe command indicates to read a value in the NVMe storagedevice, the NVMe command carries a key and a value identifier of thevalue, and the key and the value belong to the same key value pair;obtain, based on the value identifier, the value; and send the value tothe host.